This body of work was to try and identify what SSDS changes need to be made to implement some sort of security and policy enforcement for the SSDS. The first thing to do was to try and gather information about what people were looking for in access restrictions and such for their data.

Tasks

Container-based security

1. 1. Setup security domain to work with I.S.'s Centrify system
      #

Contextual-based security

Attribution Infrastructure

Interview Notes

Kanna Rajan (CANON)

I talked to Kanna about data access for CANON and his feeling was that it should not be open to the entire world, but within a group of collaborations, everyone should have access to the data that is part of the collaboration. Sort of the once you're in, you're in idea.

Francisco Chavez (CANON, BOG, Mooring)

1. Francisco mentioned that a sort of standard data policy for academics is that raw data is embargoed for 2 years, after which the PI makes it available to the public.
2. Ideally, there would be some way to automatically track all citations of data that people use for publications.
3. He felt that there would probably be some limited number of options that data providers could choose from and apply to their data. For example:
   1. Option 1: Data available to all
   2. Option 2: X Number of days embargo which nobody but the PI has access to the data after which it will be made public
   3. Option 3: X Number of days embargo which the public does not have access to the data, but a select group of collaborators might (defined by the PI). After the X number of days, that data would be available to the public.
   4. Option 4: Different groups of users have different dates of embargo. Group A has immediate access, Group B has 1 year embargo, public has 2 year embargo for example.
4. He mentioned that maybe we should look at the policies used by the Climate Data Center
5. He felt there should be some standard acknowledgement clause that tells people they need to cite the sponsors of the data they are utilizing.
6. He felt there should be some granularity within CANON to control access to various data sources (this goes against what Kanna was saying).
7. We should be able to remove people from the group of collaborations and thus remove access to the data.

Dave Caress (MDUC CTD, MDUC Navigation, Mapping AUV)

1. Some data available to all, some to collaborators
2. Other data should be embargoed

Jim Barry (MUCE, BI AUV)

Charlie Paul (MUCE)

1. Some data sources (instruments) can have their data available to the general public
2. Some data sources (instruments) will only be available to specific people (could be maintained in groups)
   1. This data might be under an embargo of some time frame
3. In all cases, MBARI and the PI should get cited when the data is used.

Bill Ussler (MUCE)

Ken Smith (Benthic Rover, BI AUV)

Chris Scholin (CANON, ESP)

Chris Grech (Ship/ROV Data)

Steve E. (Ship/ROV Data, MARS Engineering)

Nancy Jacobsen (Video)

Craig Dawe (MARS Engineering Data)

Paul McGill (MOBB)

Andy Hamilton (Power Buoy)

Ed Peltzer (FOCE)

Peter Brewer (FOCE)

Mapping AUV (Caress)

Alex Worden

Steve Haddock

John Ryan

Ken Johnson (ISUS)

Mike Godin (AOSN, LRAUV)

Jim Bellingham (AOSN, LRAUV)